1.2.2. Vendor 3

We did good tests with Vendor 3 this time.

Issues:

1. All Vendor 3’s cancellations, including cancellations for single meeting, for series or for occurrence in series, are not recognized in Vendor 2.

   1. The root cause is these cancellations do not have “ATTENDEE” section in the iCal. Vendor 2 requires this for any meeting message.

2. All Vendor 2’s cancellations, includes cancellation for single meeting, recurring series, or occurrence in series, are interpreted as “Update” in Vendor 3.

   1. The root cause is Vendor 2 doesn’t have “STATUS: CANCELLED” in the cancellation message. Notes require this section and the value has to be CANCELLED.

3. Vendor 3 uses RDATE for modified occurrence and in updating series.

   1. Vendor 2 doesn’t support RDATE. The only issues happening now is Vendor 2 couldn’t interpret Vendor 3’s update to series. The original invite to series or update to modified occurrence are good.

4. Vendor 2’s update to single occurrence of the series is not recognized correctly in Vendor 3’s application:

   1. This is because Vendor 2’s initial SEQ for such update is from 0. In Vendor 2 design, the SEQ for modified occurrence is calculated separately from Series’ SEQ.

5. Counter messages from Vendor 3 do not have Attendee status set to “Tentative”.

   1. Vendor 2 doesn’t support Counter message. It only changes the Attendee status according to the value set in the message. iCalendar generated in Vendor 3’s Counter message has “Needs-Action” for this field.

6. Vendor 2’s attachment in meeting messages are not shown up in Vendor 3.

   1. This seems to be a Vendor 3 bug so far.